Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@app/composables/usePackageComparison.ts`:
- Around line 147-155: The current .then handlers in usePackageComparison.ts
coerce missing/malformed GitHub metrics to 0 (via `|| 0`), which hides unknown
values; update the .then callbacks on the stars and issues $fetch calls so they
return null when the API payload doesn't include a numeric value (e.g., change
the arrow results for the repo stars and issues to return null for missing
values instead of 0), and keep the existing .catch(() => null). Locate the two
$fetch chains guarded by isGitHub and repoInfo (the calls that currently use
`res?.repo.stars || 0` and `res?.issues || 0`) and replace those expressions
with a check that yields null for absent/non-numeric metrics (so downstream
comparison logic can handle "unknown" rather than 0).

In `@i18n/schema.json`:
- Around line 3985-4019: The added facet keys use snake_case and must be renamed
to match the project's camelCase convention to avoid lookup mismatches: change
"github_stars" -> "githubStars", "github_issues" -> "githubIssues", and
"created_at" -> "createdAt" in the schema object (keeping their inner structure
and additionalProperties: false intact); also search for any other references to
these snake_case keys and update them to the camelCase identifiers used at
runtime so labels/descriptions resolve correctly.

In `@server/api/github/issues/`[owner]/[repo].get.ts:
- Around line 35-37: The call to $fetch<GitHubSearchResponse>(url, { headers:
GITHUB_HEADERS }) must include authentication and a request timeout to avoid
GitHub Search API rate limits; update the $fetch invocation that returns data to
add an Authorization header (bearer token read from environment/config and
merged into GITHUB_HEADERS) and a reasonable timeout option (e.g., a few
seconds) so requests fail fast and are retried/handled upstream; ensure the
token usage is conditional (fall back safely if absent) and propagate
errors/timeouts from this call so callers of this endpoint can handle
403/timeout responses.

---

Nitpick comments:
In `@test/nuxt/components/compare/FacetSelector.spec.ts`:
- Around line 35-37: The facet fixture labels in the test drift from production
locale copy—update the fixture entry keys (githubStars, githubIssues, createdAt)
so their label values exactly match the real locale strings (in particular
change createdAt's label from "Created" to "Created At") and verify any other
fixture labels mirror the app's locale source; locate these keys in the
FacetSelector.spec.ts fixture and adjust the label values accordingly.

In `@test/nuxt/composables/use-package-comparison.spec.ts`:
- Around line 196-233: Add a regression test in use-package-comparison.spec.ts
that uses usePackageComparisonInComponent and the existing
vi.stubGlobal('$fetch') pattern but returns malformed GitHub payloads (e.g.,
responses missing repo.stars or issues fields / non-numeric values) for the
GitHub endpoints; after awaiting status 'success' call
getFacetValues('githubStars')[0] and getFacetValues('githubIssues')[0] and
assert each facet's value is null (not 0) and the facet status is the expected
fallback (e.g., neutral/invalid) to ensure missing/invalid upstream shapes
produce null facet values.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@server/api/github/contributors-evolution/`[owner]/[repo].get.ts:
- Around line 30-32: The fetch call to GitHub uses
fetchGitHubWithRetries<GitHubContributorStats[]> but omits a request timeout, so
update the options passed to fetchGitHubWithRetries (the call that assigns to
data) to include a timeout (e.g. timeout: 10000) alongside maxAttempts: 6; this
ensures each retry attempt will fail fast instead of potentially blocking
indefinitely. Target the invocation of fetchGitHubWithRetries in the handler for
contributors-evolution ([owner]/[repo].get.ts) and add the timeout property to
the NitroFetchOptions object.

In `@server/utils/github.ts`:
- Around line 12-13: After destructuring maxAttempts from options (const {
maxAttempts = 3, ...fetchOptions } = options) ensure it is clamped/validated to
at least 1 before any retry loop runs (e.g. replace or follow the destructuring
with something like maxAttempts = Math.max(1, Number(maxAttempts || 0))). Apply
the same guard to the other destructurings that expose maxAttempts (the
occurrences near the other two diffs) so the retry loops using delayMs and
maxAttempts cannot be skipped when maxAttempts <= 0.
- Around line 23-28: The current merge in the $fetch.raw call loses headers when
fetchOptions.headers is a Headers instance or array-of-tuples; update the header
merge logic used before calling $fetch.raw (where defaultHeaders and
fetchOptions.headers are combined) to normalize HeadersInit into a single
Headers and then copy entries so all forms are supported: create a Headers from
defaultHeaders, then if fetchOptions.headers is a Headers, iterate its entries
and set them, if it's an array of tuples iterate and set, and if it's a plain
object iterate its keys and set; finally pass the resulting Headers (or a plain
object built from it) into $fetch.raw so callers using Headers, tuple arrays, or
objects all have their headers preserved.